Add the cache_only configuration option #1456
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @jeffkreeftmeijer looks great! |
bensie
added a commit
that referenced
this pull request
Sep 30, 2014
Add the cache_only configuration option
|
@jeffkreeftmeijer How do we use this? Your blog post doesn't show how still and I'm not sure how to set the configuration option in Carrierwave in my test_helper. Thanks for any help and for your contribution! UPDATE class ActiveSupport::TestCase
# ...
CarrierWave.configure do |config|
config.root = Rails.root.join("test/fixtures/files")
config.cache_only = true
config.enable_processing = false
config.storage = :file
end
def after_teardown
super
CarrierWave.clean_cached_files!(0)
end
end |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey everyone,
I’ve been trying to get test fixtures working on CarrierWave, and came up with a solution that works by monkey-patching
CarrierWave::Mount::Mounter#store!. That way, you prevent CarrierWave from moving the files from the cache directory to thestore_dir.It’d be great to be able to set a configuration option in your tests instead of breaking a method in the mounter, so I added a configuration option called “cache_only”, which does the same thing. What do you think?